-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci/swagger docs #9
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a big mistake. LOL
b4b5e3d
to
e7c99c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments above
why need? In order to achieve automatic, swagger docs change will follow the commit hash. create will generate new swagger docs. update will update specified version information.
7806d80
to
0a56db0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! but it would be better if you reply the swagger url to the PR
Setup integrate SwaggerHub with GitHub, generate swagger file on SwaggerHub.
Use SwaggerHub CLI
SwaggerHub CLI link
Execution conditions
Version
Version according to package.json
In PR
because only one version will be added at a time, so swaggerhub-cli use create api.
but need to upgrade the version in package.json.
https://app.swaggerhub.com/apis/Cophr/main
will use the version of package.json for this branch, so swaggerhub-cli use update api.
https://app.swaggerhub.com/apis/Cophr/test